
APAR= II09498
NETSOFT NS/ROUTER V2.00I TWINAX CONNECTIVITY


** Last updated 03/06/97 **

Client Access for Windows 95 Twinax Connectivity Information

NOTE: New Windows 95 32-bit Twinax support is now available
      in the following Client Access service packs:

      V3R1M0  SF39053
      V3R1M1  SF39059
      V3R1M2  SF39220

      Refer to Inf. APAR II10307 for complete information.
      The information in this APAR is ONLY for the older
      Windows 95 Twinax support and should not be used with
      the new support.



Contents:
I.   Before You Begin
II.  Windows 95 Preparation
III. Client Access Install and Config
IV.  Known Problems
V.   Debugging Tips

I.  Before You Begin
--------------------
HARDWARE.  The IBM Enhanced PC5250 Emulation card for
ISA PCs and the IBM Workstation Emulation card for Microchannel
PCs are supported.  At this time, the IBM PCMCIA card will
work if it is point enabled.  For instructions, please check
out the following site on the World Wide Web.
     'http://www.raleigh.ibm.com/525/525cli95.html'

For additional assistance with enabling any IBM Twinax card,
call 1-800-237-5511 and press 0 to get to an operator.
Ask for '5250 emulation' card support or the '36WSEM' group.

If using a non-IBM twinax adapter, it must be 100% hardware
compatible with the an IBM adapter that is supported.
Contact the adapter manufacturer for information,
instructions or assistance.

II. Windows 95 Preparation
--------------------------
PC RESOURCE MANAGEMENT.  The Windows 95 Plug and Play feature
handles resource management for Plug and Play compatible
hardware.  This resolves many of the traditional PC resource
management issues of the past.  But, most twinax cards
are not Plug and Play compatible.  Therefore, you need to
manually reserve all resources that the twinax card needs.  This
is best done BEFORE the twinax card is installed in the PC.

To do this, start the Device Manager of Windows 95:
  1.  Click on 'Start' (on the Windows 95 task bar)
  2.  Select Settings and then Control Panel.
  3.  Open up the 'Systems' icon.
  4.  Select the Device Manager page.
  5.  'Computer' is already selected by default.  Click
      on the properties button.

SUPPORTED CARDS.  The IBM Enhanced PC5250 Emulation card for
ISA PCs and the IBM Workstation Emulation card for Microchannel
This panel will list hardware settings that are currently in
use.  If Windows 95 does not recognize the hardware using
the setting, that piece of hardware is probably not plug and
play compatible.  If a setting is not listed on this panel,
that setting is (probably) not in use.  You will need to reserve
a setting for your twinax card to use.

Most IBM twinax cards can use any (available) IRQ between 3 and
7, inclusively.  If all the IRQs 3-7 are in use, you have to
rearrange the PC's IRQs to make one availible.  Once an IRQ
is availible, go into the Reserve Resouces page and reserve
that IRQ.

Repeat this process for any hardware setting that your
twinax card requires.  For IBM Cards, you should find an
availible setting for IRQs and Memory.  If not using an
IBM card, contact the card manufacturer or whoever supports
that card.

Most IBM cards can use memory address cc00-cfff or dc00-dfff.
One of these memory address has to be availible.  If it is not,
you will have to rearrange the PC's memory.  Note, if there is
an EMMExclude entry in the SYSTEM.INI (386Ehn section), the
Device Manager will show that memory range (in 5 digit address
form) as Unavailible for use by devices.  Once a valid
memory range has been found, reserve that address.

This can be done in one of two ways:
  1. Add a line to the SYSTEM.INI file, 386Ehn section
       EMMExclude=cc00-cfff  or
       EMMExclude=dc00-dfff  depending on which address is free
  2. In the Device Manager, Computer, Properties,
       Reserve Resources, Memory, Add.  Use
       Start value      000CC000
       End value        000CFFFF    or

       Start value      000DC000
       End value        000DFFFF
     Then, OK and reboot.

After all the needed resources have been reserved, cold boot
and verify that there are no hardware conflicts.  This can be
done by using the Device Manager and making sure that there are
no exclaimation points (!) listed on the hardware.  Or, test
each piece of hardware to verify it's operation.  If there
are any conflicts, resolve the conflicts before attempting
Client Access.

Once the proper hardware resources are reserved for the
twinax card, install the twinax card into the PC.  Try to
use the slot nearest the power supply when possible (Windows
95 Plug and Play should then find the twinax card first.)
Again, cold boot and verify that there are no hardware
conflicts.

Once this is done, proceed with III. Client Access Install
and Config.


III.  Client Access Install and Config
--------------------------------------
Install Client Access for Windows 95 and follow the steps
outlined in SC41-3512, Client Access for Windows 95 Setup.

This entails using NetSoft NS/Router as the connection
provider and then configuring a NetSoft router thru the
NetSoft Administrator.  Once this is done, you must manually
install two TSRs to run in the AUTOEXEC.BAT:

    C: PROGRA 1 IBM CLIENT 1 E5250AH /L5 /MC /Ixx
    C: PROGRA 1 IBM CLIENT 1 NSTWINAX

 note:  blank space before '1's in path should be a tilde
        /Ixx = port address (may be needed for OEM cards)

E5250AH is used for the IBM enhanced 5250 emulation card.
Replace E5250AH with WSEAH for Microchannel PCs.  Do not
use /L5 or /mc on WSEAH.

When using E5250AH, /L5 will will set the twinax card to
use IRQ 5, which is the default.  Use the interrupt that
was reserved in 'II. Windows 95 Preparation.'  The /mc
will set the twinax card to use memory address CC00-CFFF,
which is the default.  Use /md if DC00-DFFF was reserved
in 'II. Windows 95 Preparation.'

For Microchannel PCs, the twinax card hardware settings are
specified in the Reference Diskette.  These should also match
the reserves in 'II. Windows 95 Preparation.'

We are currently working on a virtual twinax driver to replace
the TSRs.

IV.  Known Problems
-------------------
1.  Configurations that are migrated from a previous twinax
environment, such as DOS Extended or CAWIN, will not work.
This is a problem that is being worked on.  The immediate
work around is to manually configure a twinax link router
instance.


V.  Debug tips
--------------
If the pc has ever had any 16-bit Netsoft product installed,
verify that it has been completely removed.  If any of the
16-bit NetSoft for Windows 3.1 code is still on the PC,
Client Access for Windows 95 may fail to connect.

Whenever possible, install the Twinax card on the bus first.
As the Plug and Play feature starts looking for devices,
it searches in bus order.  Plug and Play handles legacy
devices (non-plug and play devices like most twinax cards),
much better when it sees and configures them before plug and
play devices.

When debugging a hardware conflict, remove all adapters
from the PC and then add them in one-by-one (starting
with the twinax card) watching the Device Manager each
time a card is loaded.  If the Device Manager ever lists
an exclaimation point next to a device, resolve that conflict
before going further.

EmmExclude in the SYSTEM.INI does the same function as the
Device Manager Reserver Resources for memory.  But, the
address length is different.  SYSTEM.INI uses four digits.
The device manager uses 5 digits.  The EmmExclude=cc00-cfff
would equate to start vaule of 000CC000 and end value 000CFFFF
in the Device Manager.

If running EMM386 in CONFIG.SYS, you must have an exclusion
for the twinax card memory address.  If not, you may see
EMM386 Fatal Exception #6 at 0720:00000C00.  EMM386 is
not required for Windows 95 to operate.

Do not LOADHIGH or LH the twinax adapter handler or the
NSTWINAX module.

If you can connect on a cold boot consistently, but fail
on a warm boot, check IRQs for conflict.

Don't forget to verify that the AS/400 is ready for the
connection.  If QAUTOCFG is not turned on, the 5150 devd
must be varied on.  When in doubt, turn on auto-configuration,
delete the devd and let it recreate.  This can be done also
for the APPC ctld and devd.  But, to do this, you must vary
off the lind that the ctld is attached to (this is usually
QTDLxxxxx).

Test the connection by trying a NetSoft NS/Router connection.
This can be done by clicking on:
      Start, Programs, NS Router, NS Administator,
      double click on the router icon
      chose System and then connect button.
The bottom windows will list what is happening.  If this ends
in 'Connection failed.  This may be caused by a configuration
error' check for hardware conflicts.

To verify that the adapter handler and NSTWINAX are loading:
boot the PC, and hit escape on the cloud boot screen.  You
should see the CONFIG.SYS and AUTOEXEC.BAT processing (just
like old DOS).  Verify that no errors are displayed.  If needed,
put a pause right after the NSTWINAX.  This will automatically
pause the AUTOEXEC.BAT processing and display the text screen.
(Remember to take this out after successful connection.)

Alternative to above: After Windows is started, start
a dos prompt and MEM /C /P.  Verify that the adapter
handler and NSTWINAX load into conventional memory.

Keep the PC BIOS up to date.  Windows Plug and Play is
dependant on the BIOS' Plug and PLay ability.


Keywords:  netsoft-net-soft-w95-win95-infoapar-twinax-twinaxial
           cawin95-ca400winopt-nsrouter

